Thanks for the pull request, @rpenido!

What's next?

Please work through the following steps to get your changes ready for engineering review:

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/2u-tnl. Tag them in a comment and let them know that your changes are ready for review.

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.68%. Comparing base (77135cd) to head (317c3e7).

@@           Coverage Diff           @@
##           master    #1141   +/-   ##
=======================================
  Coverage   92.68%   92.68%           
=======================================
  Files         693      693           
  Lines       12342    12342           
  Branches     2661     2694   +33     
=======================================
  Hits        11439    11439           
  Misses        872      872           
  Partials       31       31           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@rpenido This PR should be unblocked now

Hi @bradenmacdonald !
This is ready for CC review.

@rpenido 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

@rpenido Was there a reason you squashed this PR by the way? I think that makes it a lot harder for @pomegranited to rebase her PR now, because the recent commits you've added are kind of lost in the squash.

Hi @bradenmacdonald!
It was my bad. I thought they would get lost anyway because of the squash at the merge, right?

I have the following backup branch before the squash.

https://github.com/open-craft/frontend-app-course-authoring/tree/rpenido/bkp/fal-3764-before-squash-before-conflicts

I created a PR handling the conflicts here, but it still needs some work (I may have accidentally removed something):

• Rpenido/bkp/fal 3764 before squash open-craft/frontend-app-authoring#54

I'm really sorry @pomegranited 😞

Thanks @rpenido ! It's not a big deal, but having the unsquashed branch makes it easier to merge in, especially because you had already done the work of updating your branch with the latest master.